Broadcom Confidential CPE-BEEP-PG203

December 11, 2018

CPE BEEP Linux

Broadcom Execution Environment Platform (BEEP) Application

(Developers Supplement)

Programmer’s Reference Guide

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom, the pulse logo, Connecting everything, Avago Technologies, Avago, and the A logo are among the trademarks

of Broadcom and/or its affiliates in the United States, certain other countries, and/or the EU.

The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit www.broadcom.com.

Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability,

function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does

not assume any liability arising out of the application or use of this information, nor the application or use of any product or

circuit described herein, neither does it convey any license under its patent rights nor the rights of others.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Table of Contents

Chapter 1: Introduction ...................................................................................................................... 4

1.1 Scope .........................................................................................................................................................................4

1.2 References.................................................................................................................................................................4

Chapter 2: Install Consumer Release ............................................................................................... 5

Chapter 3: Generate Firmware with BEEP ....................................................................................... 6

3.1 Toolchain ...................................................................................................................................................................6

3.2 Other Host Tools .......................................................................................................................................................6

3.3 How to Build ..............................................................................................................................................................6

Chapter 4: How to Update Firmware and Configuration ................................................................. 7

4.1 Setup ..........................................................................................................................................................................7

4.1.1 DSL Platform.....................................................................................................................................................8

4.1.2 PON Platform....................................................................................................................................................9

4.2 Update Firmware .....................................................................................................................................................12

4.3 Update Configuration File ......................................................................................................................................14

Chapter 5: BEEP Operation ............................................................................................................. 16

5.1 Flash Partition .........................................................................................................................................................16

5.2 BEEP Operation ......................................................................................................................................................17

Chapter 6: BEEP Packaging Tool .................................................................................................... 20

6.1 The beepPkgBuilder ...............................................................................................................................................20

6.2 The Package Layout ...............................................................................................................................................20

6.2.1 App-mediaType of Executable........................................................................................................................20

6.2.2 App-mediaType Tarball...................................................................................................................................21

Chapter 7: Useful Commands ......................................................................................................... 23

7.1 Attaching To The Container ...................................................................................................................................23

7.2 How to Start Container Manually...........................................................................................................................23

Chapter 8: Clock Synchronization .................................................................................................. 25

Revision History ............................................................................................................................... 26

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Chapter 1: Introduction

The CPE BEEP Programmer’s Reference Guide (Broadcom Execution Environment Application Development) is written for

OEMs when they work with third-party application developers. Broadcom is now working with the companies directly.

Additional instructions are included in this document to help developers use the Broadcom reference platform with BEEP.

1.1 Scope

This document is written for specific companies only and not for general consumers. All information in this document is

bounded to the Software License Agreement (SLA) signed between Broadcom and the company receiving this document.

This guide was written for BEEPv3 in software release 5.02L05 and BEEPv4 in software release 5.02L06.

1.2 References

The references in this section may be used in conjunction with this document.

Document (or Item) Name Number Source

[1] Introduction to Broadcom Execution Environment Platform

CPE-BEEP-AN2xx CSP (docSAFE)

[2] D-Bus Documentation

– https://dbus.freedesktop.org/

doc/api/html/

[3] D-Bus GLib bindings - Reference Manual

– https://dbus.freedesktop.org/

doc/dbus-glib/

[4] Broadcom Execution Environment Application Development

CPE-BEEP-PG1xx CSP (docSAFE)

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Chapter 2: Install Consumer Release

Use the following steps to install the consumer release.

1. mkdir release/consumer.

2. tar xzf bcm963xx_5.02L.06test2_consumer_release.tar.gz to directory created.

3. chmod +x consumer_install.

4. ./consumer_install.

The steps above install the consumer release to the directory release/consumer/bcm963xx_router.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Chapter 3: Generate Firmware with BEEP

3.1 Toolchain

Toolchain is needed to compile the code. It is normally released via docSAFE. For the 963138GW platform release 5.02L06,

the following toolchain is used.

crosstools-gcc-5.5-linux-4.1-uclibc-1.0.26-glibc-2.26-binutils-2.28.1-Rel1.10-full.tar.gz

crosstools-arm-gcc-5.5-linux-4.1-glibc-2.26-binutils-2.28.1.Rel1.10.tar.bz2

3.2 Other Host Tools

To build Broadcom reference software, the following need to be installed on the host.

This list is needed for Linux distro Ubuntu 16.04LTS.

 libncurses5-dev

 lzma-dev

 liblzma-dev

 lzma

 zlib1g-dev

 g++

 flex

 bison

 automake

 liblzo2-dev

 uuid-dev

 gcc-multilib

 g++-multilib

 Run: sudo dpkg-reconfigure dash

3.3 How to Build

1. Build a firmware image with the BEEP feature; this includes BEEP framework, a BEEP host Execution Environment (from

BEEPv4), and a Broadcom Execution Environment (BEE) package.

The package is installable to the reference platform:

cd release/consumer/bcm963xx_router

2. make PROFILE=963138GW_BEE (BEEPv3) or 963138GW_BEEP (BEEPv4).

For this platform, use the image generated under the following directory:

Release/consumer/bcm963xx_router/targets/963138GW_BEE/bcm963138GW_BEE/

bcm963138GW_BEE_nand_cferom_fs_image_128_ubi.w

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Chapter 4: How to Update Firmware and Configuration

4.1 Setup

The software package is normally downloaded into the CPE by the operator who has access to the CPE via a WAN

connection. The OEM works with third-party developers to provide them such an environment. LAN access is currently

disabled. Figure 1 shows a very basic setup of Broadcom Reference Hardware (CPE) without connecting to the operator

network. This is only used for development purposes.

Figure 1: Basic Setup of Broadcom Reference Hardware (CPE)

The WAN port is connected to a DHCP server to allocate an IP address to this port (10.1.1.2 in Figure 1). An HTTP server

is needed on the same network as the WAN port. This serves as a repository of the software packages. The operator

authorizes an application service provider to install these software packages to the CPE from the WAN connection.

The following instructions are for configuring the CPE using WebUI over LAN interface (default URL: http://192.168.1.1).

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

4.1.1 DSL Platform

1. Add a layer 2 interface by going to Advanced Setup>Layer2 Interface.

2. Pick all the default settings to set Eth0 by selecting Next and then Save/Apply.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

3. Add a WAN connection over the created Layer-2 Ethernet interface by going to Advanced Setup>WAN Service.

Select the default settings by clicking Next and Save/Apply.

A configuration file is provided to set up a WAN connection using one of the Ethernet ports (the Ethernet port closest to the

power button) as a WAN port.

4.1.2 PON Platform

A PON platform requires an additional configuration to set up the connection that is described in DSL Platform.

Before being able to set the Ethernet port as WAN, this step is necessary:

1. On the WebUI, go to the Management page to set the GBE type.

a. Use WAN select to set the Type to GBE

b. GBE MAC set to EMAC0

c. Then click Apply/Save

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

2. After the system reboots, go to the Management page to select Restore to Default system settings.

Follow the same steps as stated in DSL Platform to configure WAN over eth0 as usual. Eth0 is the Ethernet port labeled

ENET4.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

4.2 Update Firmware

Open a web browser and connection to 192.168.1.1. username is admin, and password is admin.

Under the Management menu, click Update Software. Choose the location of the firmware built in Chapter 3, Generate

Firmware with BEEP and click Update. This will cause the CPE to retrieve the firmware and reboot after it finishes flashing

it. Figure 2 shows the Update Software Web UI screen.

Figure 2: Update Software Web UI Screen

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

If the firmware is updated correctly, the software image should be 5.02L.06test2, as seen in Figure 3.

Figure 3: Device Info Screen

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

4.3 Update Configuration File

Broadcom provides a configuration file for the setup described in Setup. Under the Management menu, click Settings.

Specify the location of the configuration file to update.

Figure 4: Tools -- Update Settings Screen

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

After the configuration update, the CPE reboots and activates the new configuration. If the WAN connection is connected to

a DHCP server and retrieves the address correctly, the WAN connection information can be seen under the WAN sub-menu

under Device Info.

Figure 5 shows an example of a WAN connection configured. The IP address shown is used for WAN connection from the

WAN side. In this setup, it is 10.69.60.107.

Figure 5: WAN Info Screen

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Chapter 5: BEEP Operation

BEEP software is currently supported on ARM platforms. Depending on the number of software packages downloaded to

any execution environment, there should be a sufficient amount of flash space available to store the packages and their

configuration data. The BEEP framework itself also requires some additional flash space. For example, the framework needs

space to unwrap the package and perform digest verification. In an update operation, the framework needs to back up the

original copy so that it can fall back to it if the new version is not valid. Likewise, the memory must be sufficient for all the

applications to run on BEEP platform. The amount required is also dependent on how much memory the applications

consume.

5.1 Flash Partition

In the current release of the reference software, a partition in flash is created specifically to store modular software packages.

This section describes the procedure to create such a partition. This partition is UBIFS and the size is configurable on CFE.

1. Download the new image with the BEEP profile enabled (image updated in Update Firmware).

2. Break into CFE to change the partition 1 size using the ‘b’ command. By default, the size is set to 16M. It is recommended

to set the partition size to 100M for BEE and its deployment units. The maximum size allowed is essentially the entire

flash size minus the number of images stored in the flash, minus another 10M for PSI and others.

Voice Board Configuration (0-28) : NOSLIC

Partition 1 Size (MB) : 16M

Partition 2 Size (MB) : 0M

Partition 3 Size (MB) : 0M

Partition 4 Size (MB) (Data) : 4M

3. After completing step 2, enter the ‘r’ command to reboot.

4. Break into the CFE again and re-flash the same image one more time. After breaking into the CFE, open a Web browser

to URL http://192.168.1.1, and the image download can be done there.

5. When system reboots, enter the ‘df’ command at the CLI. The local drive should be seen. In the case below, the partition

has been set to 256M.

# df

Filesystem 1024-blocks Used Available Use% Mounted on

ububi:rootfs_ubifs 193704 38540 155164 20% /

ubi1:data 1032 48 896 5% /data

ubi2:local 55276 23056 29360 44% /local

overlay 55276 23056 29360 44% /local/modsw/tr157du/BEE/lxc/rootfs

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

5.2 BEEP Operation

Before any BEEP operation can be done, a flash partition needs to be set up to store the software packages (see Flash

Partition). Software packages can only be installed from a WAN connection. Therefore, the BEEP menu can only be seen

when the Web browser is connected from the WAN side. (Connecting to the IP address of the WAN connection is described

in Update Configuration File). The username to login from the WAN side is support and the password is admin.

Under the BEEP menu, there are three sub menus: Execution Environment, Deployment Unit, and Execution Unit, as

shown in Figure 6.

Figure 6: BEEP Screen

By default, there is a BEEP_HOSTEE built into the firmware (from version BEEPv4). The release package has the file

pkg_beep_BEE_3.0.tar.gz, that is installed from the Execution Environment sub-menu by clicking Install, and specifying

where the EE package is. After installation, the Broadcom Execution Environment is available.

Execution Environment (EE) life cycle, install, update, and uninstall, is done from the Execution Environment menu.

Likewise, the life cycle of Deployment Units (DU) is manipulated from the Deployment Unit menu. The Execution Unit life

cycle, start, and stop, is done from the Execution Unit WebUI page.

Figure 7 shows the Execution Environment Page on the Web UI.

Figure 7: Execution Environment Page

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Figure 8 shows the installation of DU screen of the Web UI. Choose EE to where DU is to be installed to, and specify where

the DU repository is and its name.

Figure 8: installation of DU screen

Figure 9 shows the summary of all the DU installed in BEE.

Figure 9: summary of DU Installed in BEE

Each DU can contain libraries and executables (also called Execution Units or EUs). Figure 10 shows the EU statuses and

the button to start or stop them.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Figure 10: Execution Unit Statuses

When Update of EE or DU is performed, the WebUI page pre-populates several fields on the page as follows.

Figure 11: EE or DU Update

DU and EE version is the version of the running DU and EE that is to be updated. This version of DU and EE is updated to

the new version of DU or EE that is specified by the DU URL or EE URL entry. The WebUI may prefill the URL with the

previous known URL, but it must be changed to point to the location where the newer version of DU or EE resides. The UUID

is a fixed ID that uniquely identifies the DU. The user must not modify this field. This information is retrieved from the entry

when the user clicks Update. In this way, the UUID is known and correct.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Chapter 6: BEEP Packaging Tool

6.1 The beepPkgBuilder

In the consumer release, the beepPkgBuilder tool can be found under the following directory:

/hostTools/beep$ ls

beepPkgBuilder.x32.save beepPkgBuilder.x64.save Makefile reposcan.x32.save reposcan.x64.save

These *.save files are binary tools for 32- and 64-bit systems. Rename the correct beepPkgBuilder *.save file for the system

to beepPkgBuilder.

6.2 The Package Layout

There are two types of package that are specified by the attribute app-mediaType in the package info file, tarball and

executable. The package builder tool expects files to be at a specific location. The example in this section should clarify this

expectation. The package builder creates a tarball from the directories of the applications.

6.2.1 App-mediaType of Executable

A package called spTestSuite has three applications/executables: spMaster, spRobot, and spSuperRobot. The package

information that is input to the beepPkgBuilder program is similar to the following:

eeName: BEE

eeVersion: 2.0

pkgName: spTestSuite

vendor: Broadcom Ltd.

description: Service Platform Test Suite provides utilities to test SP functionalities

version: 2.2

pkg-dependency:

app-name: spMaster

app-mediaType: executable

app-directory: .

app-name: spRobot

app-mediaType: executable

app-directory: .

app-name: spSuperRobot

app-mediaType: executable

app-directory: .

The app-mediaType is executable, and the app-name must be the executable name. The application directories are as

follows:

app_spMaster app_spRobot app_spSuperRobot

The directory app_spMaster contains:

spMaster spMaster.manifest

spMaster is the executable and this must be the same as app-name value specified in the pkg-info file above. The

spMaster.manifest file is the application manifest file for the spMaster program. It specifies the permission and resources

that spMaster has.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

An example of the spMaster.manifest file is given bellow:

{

"app-name": "spMaster",

"vendor": "Broadcom Ltd.",

"version": "2.1",

"description": "Master program",

"bus":

{

"wellknown-name": "com.broadcom.spMaster",

"object-path": ["/com/broadcom/spMaster"]

"linux":

{

"resources":

{

"cpu": {

"quota": 5,

"memory": {

"limit": 4000000,

"flash-size": "256KB",

"devices": [

{

"allow": false,

{

"allow": true,

"major": 3033,

"type": "c",

"access": "rw"

]

}

6.2.2 App-mediaType Tarball

The package below is an app-mediatype tarball. The package information file is as follows:

eeName: BEEP_HOSTEE

eeVersion: 3.0

pkgName: iPerf2

vendor: NLANR/DAST

description: Network Bandwidth Measurement Tool iPerf v2.0.9

version: 1.1

pkg-dependency:

app-name: iPerf2

app-mediaType: tarball

app-tarballMngrExecutable: iPerf2

app-directory: .

The content of iPerf2.manifest is:

{

"app-name": "iPerf2",

"vendor": "NLANR/DAST",

"version": "1.1",

"description": "iPerf 2.0.9 Program",

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

"user": "Super User",

"bus":

{

"wellknown-name": "com.broadcom.iperf",

"object-path": ["/com/broadcom/iperf"]

"linux":

{

"resources":

{

"cpu": {

"quota": 30

"memory": {

"limit": 50000000

"network-setup": {"mode":"Primary"},

"flash-size": "980KB"

"config":

{

"ExposedPorts":"5001/tcp,5001/udp"

"dependency":

{

"libraries": "crypt,pthread,rt,expat,ffi,dbus-1,z"

}

The iperf2 package directory contains two files as follows:

app_iPerf2

iPerf2.manifest iPerf2.tar.gz

The content of iPerf2.tar.gz is the following. The executable is under /bin/.

./bin/

./bin/iPerf2

./lib/

./lib/libstlport.so

./lib/libstlport.so.5.2.1

./lib/libstlport.so.5.2

./lib/libstlport.so.5

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Chapter 7: Useful Commands

7.1 Attaching To The Container

Developers may want to use CLI commands to debug their application. It is important to know that applications running in

Broadcom Execution Environment (BEE) is a container running inside a root container which is BEEP_BEE. The user must

attach to the root container first before being able to attach to the application's container.

Password:

> sh

BusyBox v1.29.3 (2018-10-12 10:18:35 PDT) built-in shell (ash)

Enter 'help' for a list of built-in commands.

"lxc-ls to view all the running containers

# lxc-ls

BEE::cwmpctl::15

BEE::cwmpd::16

BEE::dsldiagd::22

BEE::iPerf2::21

BEE::sambaservice::20

BEE::spMaster::17

BEE::spRobot::18

BEE::spSuperRobot::19

BEE::tr69c::14

BEEP_BEE

BEEP_ExampleEE

BEEP_HOSTEE_dsldiagd_1.1

"lxc-attach -n BEEP_BEE

"lxc-attach -n BEE::iPerf2::21

"ls bin

"# ls

bash dhcpclient kill mknod pwd start.sh

busybox echo ln mount rm tar

cat iPerf2 ls ping sh umount

cp ip mkdir ps sleep uname

7.2 How to Start Container Manually

After installing the DU package (application), follow the steps below:

1. Access the BEE container by entering: lxc-attach –n BEEP_BEE

2. Look for the application’s container name by entering: lxc-ls

The container name is the one with BEE::appname::number. For example, BEE::MyApp::1

3. Manually start the container for MyApp with ContainerName "BEE::MyApp::1":

lxc-execute -n ContainerName --share-ipc=1 – bash

For example: lxc-execute -n BEE:: MyApp::1 --share-ipc=1 – bash

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

4. At this point, you are in the container for MyApp. The application is launched by starting the executable or by using a

script. Even when the application stops or exits. The developer is still in the container.

5. If the application writes debugging info to a file, such as, /etc/logfile, the developer can directly access /etc/logfile when

in the container.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Chapter 8: Clock Synchronization

An application may need to retrieve the time setting of the system to do its functions. The gateway's time configuration is

done via the WebUI under Internet Time. Multiple time servers and a time zone can be configured. ODM is to provide a

method for application to retrieve the time server, time zone, and the current local time information.

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential CPE-BEEP-PG203

CPE BEEP Linux Programmer’s Reference Guide Broadcom Execution Environment Platform (BEEP) Application (Developers Supplement)

Revision History

CPE-BEEP-PG203, December 11, 2018

 Added DSL Platform

 Added PON Platform

 Added Chapter 8, Clock Synchronization

CPE-BEEP-PG202-R, October 28, 2018

 Updated Chapter 3, Generate Firmware with BEEP

 Updated BEEP Operation

 Added The Package Layout

 Added Chapter 7, Useful Commands

CPE-BEEP-PG201-R, September 11, 2018

 Updated Chapter 3, Generate Firmware with BEEP

 Added Chapter 5, BEEP Operation

 Updated BEEP Operation

 Added Chapter 6, BEEP Packaging Tool

CPE-BEEP-PG200-R, August 30, 2018

 Initial release

Broadcom Confidential for

dsshin2 @ humaxdigital.com

Broadcom Confidential for

dsshin2 @ humaxdigital.com